feat(remote-config, other): official onConfigUpdate API, w/Other platform support #8717
+664
−250
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR exposes the new realtime updates feature shipped in firebase-js-sdk 12.3.0 in react-native-firebase's "Other" platform implementation
Needed the same set of polyfills that the
ai
package needed, to work around react-native's deficient implementations of fetch, TextDecoder, and ReadableStreamI left the old
onConfigUpdated
APIs that have been in use since the original pre-JS-SDK implementation, but deprecated themthe new
onConfigUpdate
API has full typing etc and got its own batch of e2e tests, and is supported on all platformsRelease Summary
A single conventional commit that will trigger a feature release
Checklist
Android
iOS
Other
(macOS, web)e2e
tests added or updated inpackages/\*\*/e2e
jest
tests added or updated inpackages/\*\*/__tests__
Test Plan
The e2e tests very thoroughly probe realtime updates, and have recently been re-worked such that they are reliable in CI even (vs just running locally) so are enabled everywhere. The testing support here should be 100%, which is a good thing because the initial implementation was problematic and the e2e tests made it quite obvious it was not working.
Think
react-native-firebase
is great? Please consider supporting the project with any of the below:React Native Firebase
andInvertase
on Twitter